System and method for resource selection during group communication broadcast

ABSTRACT

Aspects of the subject disclosure may include, for example, receiving a request to initiate a multimedia broadcast multicast service (MBMS) to wirelessly distribute media content to mobile user equipment within a target geographical region using a common radio channel. An efficiency metric is obtained, in response to the request, for each broadcast multicast service center (BMSC). The efficiency metric is evaluated for each of the BMSCs and one of the BMSCs is selected based on the evaluation result. Establishment of an MBMS bearer service is facilitated using the selected BMSC, and a first media content item is disseminated to the mobile user equipment within the target geographical region using the common radio channel by way of the MBMS bearer service. Other embodiments are disclosed.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.14/851,904, filed Sep. 11, 2015, which is incorporated herein byreference in its entirety.

FIELD OF THE DISCLOSURE

The subject disclosure relates to a system and method for resourceselection during group communication broadcast.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 depicts an illustrative embodiment of a group communicationservice network;

FIG. 2 depicts an illustrative embodiment of another group communicationservice network;

FIG. 3 depicts an illustrative embodiment of a portion of a groupcommunication service networks of FIGS. 1-2;

FIG. 4 depicts an illustrative embodiment of a method used in portionsof the systems of FIGS. 1-3;

FIG. 5 depicts an illustrative embodiment of a communication system thatprovides media services, including group communication servicesaccording to the systems of FIGS. 1-3 and the process of FIG. 4;

FIG. 6 depicts an illustrative embodiment of a web portal forinteracting with the communication systems of FIGS. 1-3 and 5;

FIG. 7 depicts an illustrative embodiment of a communication device; and

FIG. 8 is a diagrammatic representation of a machine in the form of acomputer system within which a set of instructions, when executed, maycause the machine to perform any one or more of the methods describedherein.

DETAILED DESCRIPTION

The subject disclosure describes, among other things, a nodal selectionprocess between equipment of a group communication service provider andcore network elements of a mobile operator network that includesredundant, e.g., pooled, resources. The group communication servicesinclude point-to-multipoint distribution of information from a groupcommunication service source to one or more mobile communicationterminals. A process for selecting a network element or node can bedirected to implementing group communication services, by facilitatingend-to-end communication paths that establish control signaling andbearers, on demand, in a timely and cost-effective manner. Otherembodiments are described in the subject disclosure.

One or more aspects of the subject disclosure include a system includinga processor and a memory that stores executable instructions. Theexecutable instructions, when executed by the processor, facilitateperformance of operations that include receiving a request to initiate amultimedia broadcast multicast service (MBMS) to wirelessly distributemedia content to mobile user equipment within a target geographicalregion using a common radio channel. An efficiency metric is obtained,in response to the request, for each broadcast multicast service center(BMSC) of a number of BMSCs available to process the media content fordistribution to the mobile user equipment within the target geographicalregion. The number of BMSCs includes geographically diverse groups ofredundant BMSCs. The efficiency metric is evaluated for each of theBMSCs to obtain an evaluation result, wherein the efficiency metric isbased on measured parameters related to the BMSCs. One of the BMSCs isselected based on the evaluation result, and establishment of an MBMSbearer service is facilitated using the selected BMSC. A first mediacontent item is disseminated to the mobile user equipment within thetarget geographical region using the common radio channel by way of theMBMS bearer service.

One or more aspects of the subject disclosure include a process thatdetermines a request to initiate a MBMS service to wirelessly distributemedia content to mobile user equipment within a target geographicalregion using a common radio channel. An efficiency parameter isdetermined in response to the determining that the request has been madefor each BMSC of a number of BMSCs available to process the mediacontent for distribution to the mobile user equipment within the targetgeographical region. The BMSCs include geographically diverse groups ofredundant BMSCs. The efficiency parameter is evaluated for each of theBMSCs to obtain an evaluation result, wherein the efficiency parameteris based on measured parameters related to the BMSCs. A BMSC is selectedbased on the evaluation result, and establishment of an MBMS bearerservice is facilitated using the selected BMSC, wherein a first mediacontent item is disseminated to the mobile user equipment within thetarget geographical region using the common radio channel by way of theMBMS bearer service.

One or more aspects of the subject disclosure include a machine-readablestorage medium, having executable instructions that, when executed by aprocessor, facilitate performance of operations that include receiving anotification of a request to initiate a MBMS service to wirelesslydistribute media content to mobile user equipment within a targetgeographical region using a common radio channel. In response to thenotification, an operational parameter is determined for each BMSC) of anumber of BMSCs available to process the media content for distributionto the mobile user equipment within the target geographical region. TheBMSCs include geographically diverse groups of redundant BMSCs. Theoperational parameter is evaluated for each of the plurality of BMSCs toobtain an evaluation result, wherein the operational parameter is basedon measured parameters related to the BMSCs. A BMSC is identified basedon the evaluation result, and establishment of an MBMS bearer service isfacilitated using the selected BMSC, wherein a first media content itemis disseminated to the mobile user equipment within the targetgeographical region using the common radio channel by way of the MBMSbearer service.

Generally speaking, group communications can be broadcast overhigh-speed mobile data networks, such as Internet Protocol (IP) networksutilizing radio technologies, such as Long Term Evolution (LTE) andLTE-Advanced radio technologies to provide superior service quality.Examples of group communications broadcast include, without limitation,mission critical applications such as emergency, public safety and, moregenerally, any critical communication. Other group communicationservices can include entertainment applications, such as broadcast audioand/or video services. Examples can include broadcast of a live event,such as a political debate, a sporting event or reporting of newsevents.

Other group communication services can include scheduled broadcastsaccording to a program schedule, such as a program lineup according toan electronic program guide. Sources of group communication services caninclude, without limitation, public service entities, such as governmentagencies, weather bureaus, educational intuitions, e.g., offering liveand/or pre-recorded educational material or courses, traditionalbroadcast networks, network service providers, such as cable and/orsatellite service providers, on-demand providers, e.g., providing groupcommunication services in relation to a pay-per-view event, contentproducers, such as networks, cable networks, motion picture studios, andthe like.

It is understood that the application of group communication servicescan include personal broadcasting, in which an individual and/or serviceprovider provides source content for distribution to a number of mobileterminals. Source content can include personal media, playlists,personal television (TV) channels, personally obtained media such asaudio and/or video that may be obtained from pre-recorded media files,live streaming, or a combination of both pre-recorded and streamingmedia. Group communication services can include social media, such asFACEBOOK®, YOUTUBE®, and the like. It is understood further that groupcommunication services can include dissemination of advertisementcontent according to any of the systems, devices and or processesdisclosed herein.

Presently, group communication services, such as broadcast-multicastservices, over mobile IP networks technology is in an early stage ofstandards development. Accordingly, there are many opportunities forimprovement in the delivery of such services across multiple networkelements in an LTE network path, and in particular to support deliveryof services, including commercial, carrier-grade services.

An illustrative embodiment of a network architecture 100 related to thecurrent disclosure is depicted in FIG. 1. In particular, the networkarchitecture 100 disclosed herein is referred to as a GroupCommunications Service (GCS) network architecture 100, providing aone-to-many communications capability that supports a sharing ofresources, including a sharing of radio resources, such as availableradio spectrum. In more detail, the example group communications systemarchitecture 100 can be based at least in part on standards developed bythe 3rd Generation Partnership Project (3GPP) initiative, withinformation available at www.3gpp.org. By way of non-limiting example,some 3GPP standards that address group communications systemarchitecture using LTE broadcast (LTE-B) include: 3GPP TS 23.468,entitled “Group Communication System Enablers for LTE (GCSE_LTE)”; 3GPPTS 25.324, entitled “Broadcast/Multicast Control BMC”; 3GPP TS 23.041,entitled “Technical Realization of Cell Broadcast Service (CBS)” and3GPP TS 22.246, entitled “MBMS User Services,” all incorporated hereinby reference in their entireties.

In one embodiment, the group communications system architecture 100includes an access network portion 102 and a core network portion 104,e.g., an Enhanced Packet Core (EPC) or common back bone that cancommunicate with one or more external networks 106, sometimes referredto as Packet Data Networks (PDN) 106 or peer entities. The accessnetwork 102, without limitation, can include an LTE network architecturesometimes referred to as Evolved Universal mobile Telecommunicationsystem Terrestrial Radio Access (E UTRA) and evolved UMTS TerrestrialRadio Access Network (E-UTRAN). Broadly, the access network 102 caninclude one or more wireless mobile terminals or communication devices,commonly referred to as user equipment (UE) 108, and one or morewireless access nodes, or base stations 110. During network operations,at least one base station 110 communicates directly with the UE 108.

The base station 110 can be an evolved Node B (e-NodeB) in EUTRAN, withwhich the UE 108 communicates over the air and wirelessly. The UEs 108can include, without limitation, wireless devices, e.g., satellitecommunication systems, portable digital assistants (PDAs), laptopcomputers, tablet devices and other mobile devices (e.g., cellulartelephones, smart appliances, and so on). Such UEs 108 can connect tothe eNBs 110 when the UE 108 is within range according to acorresponding wireless communication technology.

The UE 108 generally runs one or more applications that engage in atransfer of packets between the UE 108 and one or more of the externalnetworks 106. Such packet transfers can include one of downlink packettransfers from the external network 106 to the UE 108, uplink packettransfers from the UE 108 to the external network 106 or combinations ofuplink and downlink packet transfers. Applications can include, withoutlimitation, web browsing, VoIP, streaming media and the like. Eachapplication can pose different Quality of Service (QoS) requirements ona respective packet transfer. Different packet transfers can be servedby different bearers within the core network 104, e.g., according toparameters, such as the QoS.

The core network 104 uses a concept of bearers, e.g., enhanced packetservice (EPS) bearers, to route packets, e.g., IP traffic, between aparticular gateway in the core network 104 and the UE 108. A bearerrefers generally to an IP packet flow with a defined QoS between theparticular gateway and the UE 108. The access network 102, e.g., EUTRAN, and the core network 104 together set up and release bearers asrequired by the various applications.

In one embodiment, the core network 104 includes various networkentities, such as a Mobility Management Entity (MME) 112, a ServingGateway (SGW) 114, a Home Subscriber Server (HSS) 116, a Policy andCharging Rules Function (PCRF) 118 and a PDN gateway (PGW) 120. In oneembodiment, the MME 112 comprises a control node performing a controlsignaling between various equipment and devices in the access network102 and the core network 104.

In at least some embodiments, the group communication networkarchitecture 100 also includes one or more of a MultimediaBroadcast-Multicast Service gateway (MBMS-GW) 126 and a BroadcastMulticast Service Center (BMSC) 124. The BMSC, among other features, cansupport MBMS broadcast mode functionality and an interface/referencepoint functionality, e.g., an MB2 reference point towards GCS-AS foractivating, deactivation and modifying an MBMS bearer associated with agroup service. The BMSC 124 traditionally provides functions for theMBMS-GW 126 that relate to user service provisioning and delivery. Forexample, the BMSC 124 issues a session start request, provided on aninterface, such as an SGmb diameter based interface. The MBMS-GW 126traditionally provides an interface for entities using MBMS bearersthrough the SGimb (user plane) reference point and an interface forentities using MBMS bearers through the SGmb (control plane) referencepoint. The MBMS-GW 126 also traditionally facilitates IP multicastand/or broadcast distribution of MBMS user plane data to E-UTRAN nodes(e.g., M1 reference points).

For illustration purposes only, the MME 112, SGW 114, HSS 116, PGW 120,BMSC 124 and MBMS-GW 126 network elements or nodes, and so on, can beserver devices, but may be referred to in the subject disclosure withoutthe word “server.” It is also understood that any form of such serverscan operate in a device, system, component, or other form of centralizedor distributed hardware and software, including virtual machines, e.g.,in relation to software defined networks. It is further noted that theseterms and other terms such as bearer paths and/or interfaces are termsthat can include features, methodologies, and/or fields that may bedescribed in whole or in part by standards bodies such as the 3GPP andIETF. It is further noted that some or all embodiments of the subjectdisclosure may in whole or in part modify, supplement, or otherwisesupersede final or proposed standards published and promulgated by3GPP/IETF.

In operation, the PCRF 118 can perform Quality of Service (QoS)management functions and policy control. The PCRF 118 is responsible forpolicy control decision-making, as well as for controlling theflow-based charging functionalities in a policy control enforcementfunction (PCEF) (not shown), which may reside in another node, such asthe PGW 120. The PCRF 118 provides the QoS authorization, e.g., QoSclass identifier and bit rates that decide how a certain data flow willbe treated in the PCEF and ensures that this is in accordance with theuser's subscription profile.

The PGW 120 can provide connectivity between the UE 108 and one or moreof the external networks 106. In the illustrative network architecture100, the PGW 120 can be responsible for IP address allocation for the UE108, as well as one or more of QoS enforcement and flow-based charging,e.g., according to rules from the PCRF 118. The PGW 120 is alsotypically responsible for filtering downlink user IP packets into thedifferent QoS-based bearers. In at least some embodiments, suchfiltering can be performed based on traffic flow templates. The PGW 120can also perform QoS enforcement, e.g., for guaranteed bit rate bearers.The PGW 120 also serves as a mobility anchor for interworking withnon-3GPP technologies such as CDMA2000 and WiFi.

With increasing use of high bandwidth applications, especially with alarge number of users receiving the same high data-rate services,efficient information distribution is essential. To this end, groupcommunications, such as broadcast and/or multicast techniques areprovided to decrease the amount of data within the network 100 and asharing of limited radio spectrum, resulting in a more efficient use ofnetwork resources. In particular, broadcast and multicast are techniquesfor transmitting data-grams from a single source, such as a GroupCommunications Service Application Server (GCS-AS) 122 to severaldestinations, e.g., point-to multipoint. The GCS-AS 122 can supportexchanging signaling, e.g., GC1 signaling (including GCS session andgroup management aspects) with UEs 108, receiving uplink data from UEs108, delivering data to all UEs 108 belonging to a group, e.g., usingunicast and or MBMS delivery, transporting application level sessioninformation, and supporting service continuity procedures, e.g., for aUE 108 to switch between unicast/MBMS delivery.

Generally speaking, a multimedia broadcast/multicast service refers to aunidirectional point-to-multipoint service in which data is transmittedfrom a single source entity to a group of users in a specific area. Thebroadcast/multicast service has two possible modes: Broadcast mode andMulticast mode. A broadcast session includes a continuous andtime-bounded reception of a broadcast service by the UE 108. Likewise, amulticast session is a continuous and time-bounded reception of amulticast service by the UE 108.

A broadcast service can be defined as a unidirectional,point-to-multipoint service in which data is efficiently transmittedfrom a single source to multiple UEs in an associated broadcast servicearea. Broadcast services may be received by all users who have enabledthe specific broadcast service locally on their UE and who are in thebroadcast area defined for the service. Likewise, a multicast servicecan be defined as a unidirectional point-to-multipoint service in whichdata is efficiently transmitted from a single source to multiple UEs inan associated multicast service area. Broadcast and/or multicastservices may be received by all users who have enabled a specificbroadcast/multicast service locally on their UE and who are in anassociated broadcast/multicast area defined for the service. It isgenerally understood that a multicast service is directed to a multicastsubscription group. For example, UE access to a multicast servicerequires a subscription associates the UE with the service.

The broadcast-multicast service area can represent the coverage area ofserved by a network, such as an entire Public Land Mobile Network(PLMN), or one or more part(s) of such a network. In some applicationsthe broadcast area can be defined individually per broadcast serviceapplication, broadcast service subscriber, and the like. For example, anemergency broadcast message can have a broadcast area associated with acontent of the message. Consider an emergency broadcast message directedto an area affected by a natural event, such as a hurricane, a flashflood or a forest fire, an Amber Alert, and the like.

For group communications services, the example network architecture 100includes an interface or reference point, designated as an MB2 interface125. The MB2 interface can include a signaling or control planeinterface, MB2-C and a data or user plane interface MB2-U. Asillustrated, the MB2 interface 125 can exist between the BMSC 124 andthe GCS-AS 122. It is understood that the particular network elements ofthe example network architecture 100 are representative. Although theMB2 reference point is disclosed in certain industry standards, it isunderstood that any reference to MB2 herein can include features ofapplicable industry standards, with or without additions, deletions andmodifications to any applicable standardized features. In at least someembodiments, the MB2 interface 125 or reference point provides anability for applications to request an allocation and/or deallocation ofa set of TMGIs, a request to activate, deactivate and modify an MBMSbearer, and for allowing the BMSC 124 to notify an application of thestatus of an MBMS bearer. In at least some embodiments, the MB2reference point 125 can include one or more other features disclosedherein, such as supporting a selection of a particular network elementand/or network configuration in relation to an establishment and/ormaintenance of any MBMS bearer services.

In some embodiments, elements of the core network 104 are located at acommon data center. In such configurations, it is understood that othercore networks (not shown) can exist in the same or different datacenters, e.g., each serving a respective geographical region.Alternatively or in addition, one or more of the elements of the corenetwork 104 can be provided in a redundant manner, such as in pool ofavailable resources. Such redundancies can be maintained within a commondata center and/or across different data centers as in providinggeographically diverse redundancies. For geographically diverse networkapplications, the GCS-AS 122 can access the MB2 interface(s) 125 of oneor more BMSCs 124 serving one or more target regions and/or markets.

In establishing a new group communication service, the BMSC 124 caninitiate a group communication service session request directed to theMBMS-GW 126. The MBMS-GW 126 responds to the BMSC 124 with sessionresponse. The MBMS-GW 126 then sends a session start request to the MME112, which sends it to the eNB 110, e.g., on an M3 Stream ControlTransmission Protocol (SCTP) based interface. In response, the eNB 110sends a session start response to the MME 112, which sends it to theMBMS-GW 126. Upon successful establishment of the session and radioresource allocation, the eNB 110 can join the transport network IPmulticast address to receive the user data from MBMS-GW 126.

An example unicast bearer path 128 is illustrated between the GCS-AS 122and the UE 108. Other network elements along the unicast bearer path128, between the GCS-AS and the UE 108, include the PGW 120, the SGW114, and the eNB 110. It is understood that unicast datagrams can berouted to the UE 108 from the GCS-AS 122. Example unicast service caninclude, without limitation, on-demand media, such as audio and/orvideo-on demand.

Likewise, an example broadcast and/or multicast bearer path 130 isillustrated between the GCS-AS 122 and the UE 108. Other networkelements along the unicast bearer path 128, between the GCS-AS and theUE 108, include the BMSC 124, the MBMS-GW 126 and the eNB 110. It isunderstood that, in some instances, broadcast and/or multicast datagramscan be routed to more than one UE 108 attached to the same eNB 110.Alternatively or in addition, broadcast and/or multicast datagrams canbe routed to more than one UE 108 attached to different eNBs 110.

Without limitation, reference to various interfaces, such as S1, S5,S11, M1, M3 and MB2 refer to EPS interfaces. In some instances, suchinterface designations are combined with a suffix, e.g., a “U” or a “C”to signify whether the interface relates to a “User plane” or a “Controlplane.” In addition, the core network 104 can include various signalingbearer paths/interfaces, e.g., control plane paths/interfaces. Thebearer paths and signaling bearer paths are only illustrated as examplesand it should be noted that additional bearer paths and signaling bearerpaths may exist that are not illustrated.

A GC1 interface 132 or reference point is illustrated between the GCS-AS122 and the UE 108. In more detail, the GC1 interface 132 can existbetween the GCS-AS and an application client on the UE 108 and can beused, for example, in roaming scenarios in which the GCS-AS 122 receivesa UE IP address, an HPLMN (home public land mobile network) ID and, inat least some instances, a VPLMN (visiting public land mobile network)ID.

The GCS-AS 122 and BMSC 124 can be connected either directly or by wayof another network element, such as a network traffic controller. Onesuch example of a network traffic controller includes a diametersignaling controller. Diameter signaling is generally understood to havea protocol that handles authentication, authorization and/or accountingmessages associated with data network communications. In someembodiments, the diameter signaling controller includes a diameter edgeagent and a diameter routing agent. FIG. 2 depicts an illustrativeembodiment of another multicast-broadcast mode network 200, in which afirst number, N, of GCS-AS 202 a, 202 b, 202 c . . . 202N, generally202, are in communication with a second number, Z, of BMSC/MBMS-GWs 206a, 206 b, 206 c . . . 206Z, generally 206, by way of a third number, Yof Diameter Signaling Routers (DSR) 204 a, 204 b, 204 c . . . 204Y,generally 204. The BMSC/MBMS-GWs 206 are in further communication with afourth number, X, of core network elements, such as MMEs 208 a, 208 b,208 c . . . 208X, generally 208. Although the BMSC/MBMS-GWs 206 areillustrated by a common symbol, it is understood that the BMSC and theMBMS-GW may, in fact, be separate devices that may be collocated, orseparate. As such, interfaces to the GCS-AS 202 would generallyterminate with the BMSC functionality, whereas, interfaces to the MMEs208 would generally terminate with the MBMS-GWs.

The GCS-AS 202 are in communication with the DSR 204 by way of a firstMB2 interface 210 a. Likewise, the DSR 204 are in communication with theBMSC/MBMS-GW 206 by way of a second MB2 interface 210 b. TheBMSC/MBMS-GW 206 are in communication with the MMEs 208 by way of an Sminterface. The MB2 interfaces 210 a, 210 b can include one or more of afirst number of protocols 214. In the illustrative example, the firstnumber of protocols 214 includes MB2-C protocol, a diameter protocol, aTCP-SCTP protocol, an IP protocol, as well as protocols associated withthe L1 and L2 interfaces or reference points. Likewise, the Sminterfaces 212 can include one or more of a second number of protocols216. In the illustrative example, the second number of protocols 216includes a protocol associated with Sm interfaces or reference points, aGPRS Tunneling Protocol GTPv2-C protocol, a UDP protocol, IP protocoland protocols associated with the L1 and L2 interfaces or referencepoints.

By way of illustrative example, each of the MMEs 208 can itself includea group or pool of MMEs 208. Alternatively or in addition, each of theBMSC/MBMS-GW 206 can be associated with a different data center and/orgeographic region. In some embodiments, each BMSC/MBMS-GW 206 cancorrespond to a respective MME pool region 208, but this need not be arequirement. In a similar fashion, the DSR 204 can be distributed acrossdifferent data centers and/or geographic regions that may or may notcorrespond to the locations of the other system components 206, 208. Asfor the GCS-AS 202, they too can be associated with respective datacenters and/or geographic regions. Alternatively or in addition, andwithout restriction, the GCS-AS 202 can be associated with groupcommunication service providers, including any of the example serviceproviders disclosed herein. In general, any of the pooled resources canbe associated with a common data center and/or common geographic region,or distributed across different data centers and/or different geographicregions.

One or more of the aforementioned connectivities 210 a, 210 b, 212 canbe established on a one-to-one basis, e.g., with a particular one of theGCS-AS 202 in communication with a particular one of the DSR 204, aparticular one of the DSR 204 in communication with a particular one ofthe BMSC/MBMS-GW 206, and/or a particular one of the BMSC/MBMS-GW 206 incommunication with a particular one of the MMEs 208. Alternatively or inaddition, one or more of the aforementioned connectivities 210 a, 210 b,212 can include connections from any one of the devices 202, 204, 206,208 to more than one of the other devices. In at least some embodiments,the devices 202, 204, 206, 208 can be connected in a mesh configuration,such as the full mesh configuration illustrated, in which any one of thedevices 202, 204, 206, 208 is connected to all of the other devicesaccording to the aforementioned interfaces.

The MB2 interfaces 210 a, 210 b disclosed herein can be distinguishedfrom the MB2 interfaces discussed in the aforementioned standards.Namely, the MB2 interfaces 210 a, 210 b can include features, e.g.,improvements at the transport and/or application layers that allow theGCS-AS 202 to select a particular one of the BMSCs 206 for TMGIallocation/de-allocation as well as performing the MBMS beareractivation, deactivation and modification steps. Selection can be basedon a predetermined logic and/or according to a set of rules.

In a large operator LTE-B network infrastructure where there may bepooled resources of network elements, e.g., pooled BMSC, MBMS GW, MME,eNBs and/or RANs (Radio Access Networks), the nodal selection processbetween the GCS-AS 206 and core network elements 206 for a given groupcommunication service can be adapted according to a selection criteria.For example, the selection criteria can include efficiency and/or costto preferentially establish MBMS service in an efficient andcost-effective manner across the end-to-end communication path. Suchefficient and cost effective nodal selections support an establishmentof related signaling and bearers, on demand, and in a timely manner.Alternatively or in addition, the selection criteria can includereliability and/or a preference for particular equipment, such as apreferred vendor equipment and/or a preferred software configuration.

By way of example, an intelligent process for dynamic selection of theBMSC core network element 206 by the GCS-AS 202 over the MB2-C interface210 a, 210 b can be based on one or more performance metrics, such asutilization factors, mapped LTE-B serving areas, proximity betweendevices 202, 210 to synthesize a network configuration according to thecriteria, such as having an optimal, or best possible BMSC node. Such asynthesized solution can facilitate an MBMS session and MBMS bearer tosupport delivery of the group communication service content to mobiledevices 108 (FIG. 1) efficiently in a given targeted coverage area toprovide a superior high-speed mobile broadcast experience.

In support of the node selection process, the network architecture 200can include or otherwise access other network elements. A first networkelement includes an Operation Support System (OSS) 220. Generallyspeaking, the OSS 220 is s a set of equipment, programs, tools and/orutilities that help a communications service provider monitor, control,analyze and manage a communications network. To this end, the OSS 220can be in communication with one or more of the network devices, e.g.,including the MMEs 208 and/or the BMSC/MBMS-GW 206. The OSS 220 canmonitor or otherwise determine configurations and/or performance metricsassociated with the devices 208, 206, their individual performanceand/or performance of systems and subsystems determined fromcombinations of one or more devices of the network 100, 200.

Examples of monitored features can include, without limitation, identityof active/passive network elements, geographic locations, networkconfiguration(s), network element configurations, equipment vendors,network operators, utility, availability, congestion, capacity and/orreliability of individual network elements and/or of portions of thenetwork, or of the network as a whole. Such features, values and/orresults can be stored, e.g., in a first data store 222 accessible by theOSS 220.

In some embodiments, the OSS 220 access such features in real time,e.g., directly from the network devices. Alternatively or in addition,the OSS 220 can access historical records of such features to obtainpredictions of one or more of the monitored network features. Suchpredictive features can account for daily variations, e.g., in networktraffic, usage of particular devices as it may relate to reliability,e.g., mean-time-between failures based on hours of operation and/orfailure records, and the like.

In some embodiments, the network architecture includes a GroupCommunication Service (GCS) management engine 224. The GCS managementengine 224 can be in communication with the OSS 220 and/or storage 222,and with one or more of the network elements, such as the BMSCs and/orthe MBMS-GWs. In some embodiments, the GCS management engine 224 is infurther communication with one or more of the GCS-AS 202. Such networkconnectivity can be facilitated by the DSR 204 and/or by other means,such as a separate or sideband channel.

Although the GCS management engine 224 is illustrated as a separatedevice, it is envisioned that at least a portion of the relatedfunctionality can be included or otherwise embedded in one or more ofthe devices. For example, in some embodiments, the GCS management engine224 is incorporated into the BMSC and/or the MBMS-GW 206. Alternativelyor in addition, the GCS management engine 224 can be incorporated intothe GCS-AS 202.

The GCS management engine 224 can be operable to perform any of thevarious node selection techniques and processes disclosed herein. Forexample, the GCS management engine 224 can receive a request from aGCS-AS 202 to initiate a group communication to a particular geographicregion and/or target UEs 108 (FIG. 1). The GCS management engine 224 canidentify available options of equipment and network connectivity, obtainfeature and/or metrics associated with the identified equipment, performtradeoffs between different available combinations, and compare tradeoffresults to identify a synthesized solution or selection, e.g., as a mostefficient, reliable and/or cost-effective. The relative terms, such asmost efficient, reliable or cost effective can be made in reference to aset of possible or candidate solutions that may include a subset of allpossible solutions or network configurations, and in at least someinstances, including all possible solutions or network configurations.

It is envisioned that other rules can be implemented in the decisionprocess. For example, a particular group communication service providermay identify a preference based on vendor equipment, data centers,geographic locations and the like. Such rules can be programmed orotherwise implemented in the GCS management engine 224, e.g., during aconfiguration of the network 200. It is also understood that such rulescan be reprogrammed at various times and/or based upon occurrences ofcertain events.

In an LTE-B reference network architecture, the GCS-AS 202 interfaceswith the BMSC 206 to establish control plane connectivity prior toinitiating a group communication application. Upon successful set up,the GCS-AS 202 can request for allocation of MBMS bearers to initiatethe GCS to a targeted region and/or group of user equipment. Thesebearers can be identified by unique flow identifiers or TMGIs (TemporaryMobile Group Identities) and assigned a certain QoS.

Referring to the example broadcast core network 200 illustrated in FIG.2, there could be multiple regional pools of MMEs 208, DSRs 204,MBMS-GWs and BMSCs 206 serving various RAN markets with common and/ordifferent vendor combinations. Network configurations can includededicated GCS-AS nodes 202 deployed in a geo-redundant load-sharedpooled configuration to support such critical GCS. The GCS-AS 202 andBMSC 206 can be arranged in a peered connectivity model or there couldbe a shared configuration, e.g., including a full mesh connectivitybetween groups of GCS-AS 202 and BMSCs 206 via centralized DSR 210 for aflexible architecture design, as illustrated.

To support such a design, the MB2-C interface 210 implementation on theBMSC 206 and GCS-AS 202 can be pre-programmed or otherwise modified toinclude intelligence in one or more of the BMSC selection and routing oftraffic from GCS-AS 202 towards selected BMSC 206 during normal,overload, nodal error and failover conditions. References tointelligence can include predetermined logic and/or rules. In someinstances, such intelligence can include a learning feature, e.g., inwhich previously determined GCS solutions and/or selections are used todetermine a current or future solution. It is understood that in atleast some instances intelligence can include elements of artificialintelligence. In some embodiments, the “Y” BMSC nodes 206 can act as thegate keepers from the N GCS-Ass 202 for specific group communicationfrom various regional/public safety communication service providers intothe operator's LTE broadcast network. It is worth noting that thenumbers X, Y, Z and N referred to herein can include any numberextending from 1 to some number greater than one. Additionally, it isunderstood that at least some of the numbers X, Y, Z and N can be equalto or different from the others.

In such a fully meshed connectivity model, all BMSCs 206 can potentiallyobtain the TMGI allocation and de-allocation requests from a givenGCS-AS 202 or multiple such GCS-AS 202 based on the specific service atany given time. However, the operator could enforce a policy to utilize1 of the “N” BMSCs 206 as a primary application ingestion source for theGCS provider based on pre-defined selection criteria and to optimize theresource allocation mechanisms.

This disclosure provides a mechanism for selection of the BMSC 206 inassociation with a GCS-AS 202 to initiate the resource allocation andMBMS bearer activation process. The GCS management engine 224, sometimesreferred to as a unified BMSC resources management engine, utilizes acombination of real-time BMSC resource utilization metrics, serving areamapping, peak loading and latency factors to determine the best possibleBMSC that can be used by a GCS AS for a specific GCS.

In a simplistic network design, one BMSC 206 a and one GCS-AS 202 alocated in the same or separate data centers can be connected in pairedmode to establish a one-to-one diameter peer relationship and exchangeMBMS bearer related procedures via the MB2-C diameter interface 210.Such a paired mode of operation may be suitable for a limited scalenetwork deployment to deliver GCS from a given provider set. In sucharchitectures, the BMSC 206 a and GCS-AS nodes 206 a may be limited bytheir platform specific, connectivity, redundancy, scalability andcapacity performance constraints. Such a solution may not scale easilyif more LTE users or machine-to-machine (M2M) devices become interestedor need to be delivered with such group services, e.g., in relation toan Internet of things application.

For a large scale mobility network infrastructure design, such peeredoperation may not represent the best option due to several constraintssuch as equipment location, connectivity towards multiple BMSC corenetwork elements in distributed data centers, serving LTE customer base,new LTE broadcast group services offering, anticipated user datacapacity for a given GCS, session/bearer capacity, broadcast servingareas, regionalized group content distribution etc.

To deliver a superior end user LTE broadcast based GCS experience andrightfully conserve the spectrum as well as unicast network resources,the core network requires a flexible architectural design option, e.g.,consisting of multiple GCS-AS 202 and BMSC 206 nodes. In such a pooledresource environment, the BMSC selection process by the GCS-AS 202 canbe implemented by anchoring one of the BMSCs 206, e.g., the “right” BMSC206, as a session initiation source for sending high-qualitycommunication (audio/video/messaging) content towards a targeted groupin a given broadcast serving area. References to the right BMSC 206 canrefer to a BMSC 206 selected from a pool of BMSCs according to thetechniques disclosed herein.

The “Y” BMSCs 206 can be reached from the “N” GCS-Ass 202 via the “Z”regional DSRs 204 in a fully connected mesh topology. In such a design,the diameter peers are cross-connected via DSRs 204 to establishdiameter connections towards each other. The network elements 206, 204,202 can exchange capabilities between each other to learn of thediameter host names for further application layer message exchanges suchas the bearer activation, deactivation, modification and statusindication procedures.

If a regional DSR 204 or the link between a DSR 204 and a BMSC 206 or alink between GCS-AS 202 and a DSR 204 fails due to any reasons, theBMSCs 206 and GCS-Ass 202 can still communicate via alternate routingand/or redirection towards another regional DSR 204 based on the MB2-Capplication identifier, a message type and/or its priority.

Based on GCS provisioning, the operator may select one or a subset ofthe “N” BMSCs 206 for a given GCS broadcast session. Each of the BMSCs206 in the mesh connectivity model can extract its utilization factorsretrieved from the OSS analytics engine 220 on a periodic polling basisand stored in a mapping table on the storage device 222. The BMSCs 206report their utilization metrics to the OSS 220 based on anoperator-predefined configuration interval.

In some embodiments, the same mapping table can store the round triptime latency measurements, e.g., obtained from the BMSCs 206 towardseach of the MBMS-GWs 126 (FIG. 1)/GCS-ASs 202 over their respective SCTPtransport layer protocol, as well as map the serving area identities(SAI) and MMEs serving those SAIs. Such a mapping table and look upalgorithm in the BMSCs 206 updated in near real time can be used toselect a “best possible” pair of BMSC-GCS-AS and BMSC-MBMS-GW 206 for aparticular GCS session setup and user data transfer.

The LTE-broadcast GCS architecture can be utilized for a variety ofregional or nation-wide emergency as well as public safety relatedcritical group communications delivery across a desired broadcastserving area to relieve the unicast network resources. The GCS-AS 202can leverage the network level intelligence provided by the BMSC 206pool management and user analytics to be able to decide if a GCSsession/bearer activation needs to be setup in a unicast or broadcastmode.

In case of any issues with a given BMSC 206 or set of BMSCs 206 or ifthe round-trip time from these BMSCs 206 towards the GCS-AS 202 exceedsan operator provisioned critical threshold, the BMSC pool managementsystem can be implemented with a capability to blacklist those BMSCs 206for a certain duration and once they come out of such criticalcondition, those BMSCs 206 can be removed from the blacklist and madeavailable for GCS services.

Such an intelligent BMSC selection within the pool environment can helpin preventing potential LTE-broadcast GCS related mission criticalservice outages in the mobility network. The GCS-AS 202 can choosealternate BMSCs 206 based on the mapping table 222, provisioning rulesand ensure seamless GCS continuity in case of data center disastersituations.

The BMSC 206 and MBMS-GW 126 (FIG. 1) network elements can be integratedin a direct-peered mode connectivity model for simplicity of networkdesign and operation. They can also be connected via the centralized DSR204 regional pool in an alternate mesh connectivity model. Such anarchitecture is preferred for a fully flexible LTE-B core network designas it eases the technical requirements on standalone BMSC and MBMS GWnodal design for capacity, scalability and reliability.

The “Y” BMSCs 206 can be connected to the “N” GCS-AS nodes 202 in afully mesh topology although the right BMSC 206 can still be selected bythe primary GCS-AS 202 to be able to optimally deliver the high qualityGCS content to the end users. Once a primary BMSC node 206 has beendesignated and selected for a given GCS service, that BMSC 206 can theninitiate the MBMS-GW selection and MBMS session setup procedures towardsthe MBMS-GW. The MBMS-GW interfaces to the MME and eNB for control anduser plane interactions to complete the session setup for enabling GCSservice to the end users.

The GCS-AS 202 can extract user intelligence from the OSS system 220 tobe able to select between the broadcast and unicast delivery modes inthe downlink direction for application signaling and data. In theuplink, the UE 108 (FIG. 1) uses EPS bearer services to exchangeapplication signaling and data. Dynamic join/leave/modify/control cantake place when the UE 108 decides to enter/exit/change control for aspecific GCS that it may have subscribed to as part of the overall GCSservice offerings and as allowed by the network layer.

When users move between areas where there may not be contiguous GCS overbroadcast bearers, the UE 108 can inform via underlying unicast or 3Gnetwork its desire to change from broadcast GCS mode to unicast mode ordisable GCS temporarily until it gets back into the broadcast/unicastLTE coverage area. To maintain service continuity for GCS in transit, UEcould potentially receive duplicate signaling and data that could bediscarded based on network assisted feedback.

FIG. 3 depicts an illustrative embodiment of a portion of an MBMSnetwork architecture 300, such as the network architectures of FIG. 1 orFIG. 2 that includes features of software defined networking (SDN), suchas one or more virtual machines. Applications of SDN techniques allow anetwork administrator to manage network services, such as MBMS services,through abstraction of higher level functionality.

By way of example, one or more virtual machines can be configured toimplement the nodal functions of an MBMS network, such as the GCSnetwork architectures 100, 200 (FIGS. 1 and 2). Consider a first classof virtual machines implementing a BMSC 306, a second class of virtualmachines implementing one or more of the core logic functions, such asan MME 312 and/or an MBMS-GW 326, a third class of virtual machinesimplementing the DSR 304′, 304″, and a fourth class of virtual machinesimplementing the OSS 320. In the illustrative example, the virtual OSSmachine 320 also includes virtual network function management.

The different virtual machines can be provisioned, configured andotherwise maintained by the same or different entities. Partitioning ofthe virtual machines, e.g., as indicated can be beneficial according toany different entities. Alternatively or in addition, a single virtualmachine can implement two or more of the different classes of virtualmachines. Moreover, the consolidated MBMS network architecture 300provides the opportunity to reclaim power, floor space, HVAC, andtransport connections formerly occupied or otherwise supported by legacy3G network elements and/or multiple, discrete platforms supportingLTE/4G core network functions. Network virtualization, e.g., in theconsolidated MBMS networks 100, 200 allows for the use of virtualmachine(s). The virtual machines can include an emulation of a computersystem. The emulated computer system can include software, such asoperating software, application software, and the like, to emulate anyof the network elements and/or nodal functions disclosed herein. Thevirtual machines can include various configurations that can includededicated hardware, shared hardware, specialized hardware, networkedhardware, and the like.

In operation, to initiate a new MBMS, a requesting GCS-AS 202 sends aGCS-Action Request (GAR) command to one or more of the BMSCs 204. TheGAR includes an MBMS-Bearer Request that can include further detail,such as a Temporary Mobile Group Identity (TMGI), an MBMS service area,QoS information, duration, start and/or stop times, and the like.Generally, the TMGI uniquely identifies the MBMS bearer service. TheBMSC 206 allocates resources in the MBMS system 100, 200 to support dataflow. For GAR commands that do not include a TMGI value, one can beassigned by the BMSC 206. In at least some embodiments, the BMSC 206 canbe configured to determine whether a requesting GCS-AS 202 is authorizedfor the requested MBMS service, responding to a GAR accordingly.

Details related to an MBMS service area can include a list of MBMSService Area Identities (SAIs). MBMS service areas can be preconfigured,e.g., in the BMSC 206, allowing the BMSC 206 to map the service area(s)to a list of serving cells. The BMSC 206 can interpret other details,such as the QoS, and identify any parameters related to provision of therequested MBMS service to the identified list of serving cells. Forexample, identified parameters can include one or more of a bit errorrate, bandwidth, delay, and the like. The BMSC 206 uses the parametersto establish MBMS bearers to equipment at the identified serving cells,such as eNBs 110 in the MBMS service area. To this end, the GCS-AS 202uses an identifier, such as the TMGI and Flow ID to identify aparticular MBMS delivery session. Once the bearer has been establishedby control plane signaling information, the GCS-AS 202 uses the TMGI andFlow ID to identify the established MBMS delivery session. Establishmentof the MBMS bearer can include identification of an IP address and portnumber of the BMSC 206 for routing user-plane traffic. MBMS data isdirected from the GCS-AS 202 to the BMSC 206 in a user-plane, e.g.,containing an IP address and port number of the BMSC, thereby allowingthe GCS-AS to send the media to UE within the MBMS service area.

FIG. 4 depicts an illustrative embodiment of a process 400 used inportions of the system described in FIGS. 1-3. In particular, theprocess 400 includes a nodal selection process between equipment of agroup communication service provider and core network elements of amobile operator network that includes redundant resources that can beprovided in a pooled arrangement. An indication of a request for GroupCommunication Service (GCS) is received at 402. Such requests can bereceived from one or more of a network or communication serviceprovider, a media content provider, a group and even an individual, whomay wish to initiate a broadcast or multicast service. In someembodiments, the request can be received by the GCS-AS 202.Alternatively or in addition, the request can initiate from anothersource, such as equipment of the service provider, the media contentprovider, the group or individual. In such instances, the request can bereceived from such other entities at the GCS-AS 202, which in turn, canresult in an internal request for GCS service directed from the GCS-AS202 towards the network, including a network management or controller.

A GCS node selection criteria is identified at 404. Such criteria caninclude a goal or preference of any synthesized or resulting networkand/or routing configurations. Example preferences include, withoutlimitation, efficiency, e.g., according to network resource utilization,costs, e.g., network operating costs, region and/or location, networkoperator, equipment vendor, and the like. The GSC node selectioncriteria can be identified as a default, e.g., established during aconfiguration of LTE-B service support, and applied to all requests forGCS services. Alternatively or in addition, the node selection criteriacan be provided by one of a requesting entity, an associated GCS-AS 202and/or related GCS application. Such selection criteria can once again,be established during a configuration of equipment and/or applications,or entered on a per request basis.

A candidate GCS network node 202 is identified based on request at 406.Candidate GCS network nodes 202 can be identifies according to adefault. For example, default GCS network nodes can be associated orotherwise paired to one or more of the GCS-ASs 202. Such associations orpairings does not necessarily indication that the paired nodes will beused in a resulting GCS bearer service. Other GCS nodes can beidentified based on criteria of the GCS request. This might include ageographical GCS service area, nodes of a particular service providerand/or of a particular vendor and/or configuration.

Identification of nodes can include a process for expanding a default,preferred, or preconfigured node to one or more other nodes. Suchexpansion of candidate nodes can be accomplished according topre-programmed logic and/or rules. For example, alternative candidatenodes can be selected randomly from pools of such nodes. Alternativelyor in addition, node selection can include representative sample nodesfrom different data centers, different geographic regions, differentnetwork providers, different vendors, different configurations, and thelike. The number of candidates identified can range from an open endedsolution of all possible candidates, to some finite value, e.g., 100,10, 2 or even 1. If a preferred value has been established, such as 100,but the network configuration cannot support that number ofalternatives, the number can be all possible candidate networks, i.e.,all possible candidates up to some predetermined number.

Metrics of candidate GCS network node are determined at 408. Metrics,without limitation, can include any category of metrics disclosedherein, such as efficiency, round-trip-transit times, utilization,capacity, congestion, reliability, operating costs, and so forth. Insome embodiments, the metrics can be monitored, e.g., in a routinemanner by an OSS system. Alternatively or in addition, the metrics canbe obtained, updated or otherwise determined in response to a requestfor GCS service. In some embodiments, the metrics can include one ormore of historical records, statistical values related to the records,such as averages, maxima, minima, and so forth.

In at least some embodiments, the metrics can include trends. Trends canbe determined by processing current and/or historical metrics. Forexample, trends can include a rate of change of a particular metric.Consider a utilization metric. The current value may be relatively low,but the utilization may be increasing rapidly, as may result from any ofusage, time of day, events and the like. In some embodiments, metricscan include combinations of more than one metric. Consider utilizationcombined with round-trip-transit and/or operating costs. Combination ofsuch different metrics can be determined according to a preprogrammedalgorithm and or business rule. Such algorithms and/or rules can beimplemented in one or more of the network nodes disclosed herein, or bya separate device, such as a server of a GCS service provider.

A determination is made as to whether a selection criteria as beensatisfied at 410. In obtaining such a determination, the selectioncriteria can be applied to one or more of the candidate network nodesalone or in combination based on the applicable metrics. To the extentthat the selection criteria have not been satisfied, identifyalternative candidate GCS network node based on request at 412. In someembodiments, the determination can include identifying a particularnetwork node that satisfies the criteria. This might be the first of oneor more network node candidates. For example, if ten candidates areidentified, each candidate can be evaluated in a sequential manner untilone of the candidates satisfies the selection criteria. Once one hasbeen identified, evaluation can stop, as there is no need for furtherevaluation of other options.

In other embodiments, however, multiple candidate solutions areevaluated, and one particular solution can be selected from amongseveral otherwise suitable options. For example, one or more metrics ofeach of a number of candidate network nodes can be evaluated resultingin respective evaluation values. A determination of the selectioncriterial can include a comparison of the multiple options to identify apreferred option. Such preferences can include, without limitation, theoption having the greatest or least value of the particular metric fromamong the available candidates.

To the extent that the selection criteria has satisfied, facilitate GCSbearer service based on candidate GCS network node at 414. Facilitationof a GCS bearer service can include techniques disclosed in relation tothe aforementioned MB2 standardized interface. Once the BCS, e.g., MBMSbearer has been established, GCS datagrams or packets can be directed tothe UE 108 through the GCS network 100, 200, 300.

While for purposes of simplicity of explanation, the respectiveprocesses are shown and described as a series of blocks in FIG. 4, it isto be understood and appreciated that the claimed subject matter is notlimited by the order of the blocks, as some blocks may occur indifferent orders and/or concurrently with other blocks from what isdepicted and described herein. Moreover, not all illustrated blocks maybe required to implement the methods described herein.

FIG. 5 depicts an illustrative embodiment of a first communicationsystem 500 for delivering media content. The communication system 500can represent an Internet Protocol Television (IPTV) media system.Communication system 500 can be overlaid or operably coupled with themulticast-broadcast networks 100, 200, 300 of FIGS. 1, 2 and/or 3, asanother representative embodiment of communication system 500. Forinstance, one or more devices illustrated in the communication system500 of FIG. 5 can obtain characteristics of a number of broadcastprocessors that process media content for broadcast transmission toequipment of a number of users. The number of broadcast processorsincludes a number of geographically diverse groups of redundantbroadcast processors, such as BMSC and/or MBMS-GWs of a mobility corenetwork 580. The operations further include determining a broadcastefficiency metric based on the characteristics of the number ofbroadcast processors and selecting one or more broadcast processorsbased on the efficiency metric. An allocation of mobility networkresource is initiated based on the selected broadcast processor(s), andestablishment of a broadcast bearer is facilitated using the selectedbroadcast processor(s), wherein a first media content item is broadcastto the equipment of the plurality of users by way of the broadcastbearer.

The IPTV media system can include a super head-end office (SHO) 510 withat least one super headend office server (SHS) 511 which receives mediacontent from satellite and/or terrestrial communication systems. In thepresent context, media content can represent, for example, audiocontent, moving image content such as 2D or 3D videos, video games,virtual reality content, still image content, and combinations thereof.The SHS server 511 can forward packets associated with the media contentto one or more video head-end servers (VHS) 514 via a network of videohead-end offices (VHO) 512 according to a multicast communicationprotocol.

The VHS 514 can distribute multimedia broadcast content via an accessnetwork 518 to commercial and/or residential buildings 502 housing agateway 504 (such as a residential or commercial gateway). The accessnetwork 518 can represent a group of digital subscriber line accessmultiplexers (DSLAMs) located in a central office or a service areainterface that provide broadband services over fiber optical links orcopper twisted pairs 519 to buildings 502. The gateway 504 can usecommunication technology to distribute broadcast signals to mediaprocessors 506 such as Set-Top Boxes (STBs) which in turn presentbroadcast channels to media devices 508 such as computers or televisionsets managed in some instances by a media controller 507 (such as aninfrared or RF remote controller).

The gateway 504, the media processors 506, and media devices 508 canutilize tethered communication technologies (such as coaxial, power lineor phone line wiring) or can operate over a wireless access protocolsuch as Wireless Fidelity (WiFi), Bluetooth®, Zigbee®, or other presentor next generation local or personal area wireless network technologies.By way of these interfaces, unicast communications can also be invokedbetween the media processors 506 and subsystems of the IPTV media systemfor services such as video-on-demand (VoD), browsing an electronicprogramming guide (EPG), or other infrastructure services.

A satellite broadcast television system 529 can be used in the mediasystem of FIG. 5. The satellite broadcast television system can beoverlaid, operably coupled with, or replace the IPTV system as anotherrepresentative embodiment of communication system 500. In thisembodiment, signals transmitted by a satellite 515 that include mediacontent can be received by a satellite dish receiver 531 coupled to thebuilding 502. Modulated signals received by the satellite dish receiver531 can be transferred to the media processors 506 for demodulating,decoding, encoding, and/or distributing broadcast channels to the mediadevices 508. The media processors 506 can be equipped with a broadbandport to an Internet Service Provider (ISP) network 532 to enableinteractive services such as VoD and EPG as described above.

In yet another embodiment, an analog or digital cable broadcastdistribution system such as cable TV system 533 can be overlaid,operably coupled with, or replace the IPTV system and/or the satelliteTV system as another representative embodiment of communication system500. In this embodiment, the cable TV system 533 can also provideInternet, telephony, and interactive media services. System 500 enablesvarious types of interactive television and/or services including IPTV,cable and/or satellite.

The subject disclosure can apply to other present or next generationover-the-air and/or landline media content services system.

Some of the network elements of the IPTV media system can be coupled toone or more computing devices 530, a portion of which can operate as aweb server for providing web portal services over the ISP network 532 towireline media devices 508 or wireless communication devices 516.

Communication system 500 can also provide for all or a portion of thecomputing devices 530 to function as a GCS-AS 530. The GCS-AS 530 canuse computing and communication technology to perform function 562,which can include among other things, the broadcast-multicast techniquesdescribed by process 400 of FIG. 4. For instance, function 562 of theGCS-AS 530 can be similar to the functions described in one or more ofthe OSS systems 220, 320 and/or the broadcast-multicast managementengines 224, 324 of FIGS. 2-3 in accordance with process 400. The mediaprocessors 506 and wireless communication devices 516 can be provisionedwith software functions 564 and 566, respectively, to utilize thebroadcast-multicast services of GCS-AS 530. For instance, functions 564and 566 of media processors 506 and wireless communication devices 516can be similar to the functions described for the communication devices108 of FIG. 1 in accordance with process 400.

Multiple forms of media services can be offered to media devices overlandline technologies such as those described above. Additionally, mediaservices can be offered to media devices by way of one or more wirelessaccess base stations 517 operating according to common wireless accessprotocols such as Global System for Mobile or GSM, Code DivisionMultiple Access or CDMA, Time Division Multiple Access or TDMA,Universal Mobile Telecommunications or UMTS, World interoperability forMicrowave or WiMAX, Software Defined Radio or SDR, Long Term Evolutionor LTE, and so on. Other present and next generation wide area wirelessaccess network technologies can be used in one or more embodiments ofthe subject disclosure. The base stations 517 can be in communicationwith the GCS-AS 530 through one or more mobility core networks 580, suchas the group communication service network architectures 100, 200, 300of FIGS. 1, 2 and/or 3. In particular, the mobility core network(s) 580can be adapted to include functionality 568 to utilize thebroadcast-multicast services of the GCS-AS 530 according to thetechniques disclosed herein, e.g., including the process 400 of FIG. 4.

FIG. 6 depicts an illustrative embodiment of a web portal 602 of acommunication system 600. Communication system 600 can be overlaid oroperably coupled with the broadcast-multicast systems 100, 200, 300 ofFIGS. 1, 2 and/or 3, communication system 500, and/or communicationsystem 500 as another representative embodiment of thebroadcast-multicast systems 100, 200, 300 of FIGS. 1, 2 and/or 3,communication system 500, and/or communication system 500. The webportal 602 can be used for managing services of systems 100, 200, 300 ofFIGS. 1, 2 and/or 3 and communication system 500. A web page of the webportal 602 can be accessed by a Uniform Resource Locator (URL) with anInternet browser using an Internet-capable communication device such asthose described in FIGS. 1, 2 and/or 3 and FIG. 5. The web portal 602can be configured, for example, to access a media processor 506 andservices managed thereby such as a Digital Video Recorder (DVR), a Videoon Demand (VoD) catalog, an Electronic Programming Guide (EPG), or apersonal catalog (such as personal videos, pictures, audio recordings,etc.) stored at the media processor 506. The web portal 602 can also beused for provisioning IMS services described earlier, provisioningInternet services, provisioning cellular phone services, and so on.

The web portal 602 can further be utilized to manage and provisionsoftware applications 562-568, to adapt these applications as may bedesired by subscribers and/or service providers of the systems 100, 200,300 of FIGS. 1, 2 and/or 3, and communication systems 500. For instance,users of the services provided by GCS-AS 330 or server 530 can log intotheir on-line accounts and provision the servers 110 or server 530 withgroup communication services, subscribed and/or operational parametersrelated to group communication services, such as group communicationservice areas, lists of subscribers, technical features, including QoS,start and/or stop times, security features, and the like to enable it tocommunication with devices described in FIGS. 1-5, and so on. Serviceproviders can log onto an administrator account to provision, monitorand/or maintain the systems 100, 200, 300 of FIGS. 1, 2 and/or 3 orserver 530.

FIG. 7 depicts an illustrative embodiment of a communication device 700.Communication device 700 can serve in whole or in part as anillustrative embodiment of the devices depicted in FIGS. 1, 2 and/or 3,and FIG. 5 and can be configured to perform portions of the process 400of FIG. 4.

Communication device 700 can comprise a wireline and/or wirelesstransceiver 702 (herein transceiver 702), a user interface (UI) 704, apower supply 714, a location receiver 716, a motion sensor 718, anorientation sensor 720, and a controller 706 for managing operationsthereof. The transceiver 702 can support short-range or long-rangewireless access technologies such as Bluetooth®, ZigBee®, WiFi, DECT, orcellular communication technologies, just to mention a few (Bluetooth®and ZigBee® are trademarks registered by the Bluetooth® Special InterestGroup and the ZigBee® Alliance, respectively). Cellular technologies caninclude, for example, CDMA-1X, UMTS/HSDPA, GSM/GPRS, TDMA/EDGE, EV/DO,WiMAX, SDR, LTE, as well as other next generation wireless communicationtechnologies as they arise. The transceiver 702 can also be adapted tosupport circuit-switched wireline access technologies (such as PSTN),packet-switched wireline access technologies (such as TCP/IP, VoIP,etc.), and combinations thereof.

The UI 704 can include a depressible or touch-sensitive keypad 708 witha navigation mechanism such as a roller ball, a joystick, a mouse, or anavigation disk for manipulating operations of the communication device700. The keypad 708 can be an integral part of a housing assembly of thecommunication device 700 or an independent device operably coupledthereto by a tethered wireline interface (such as a USB cable) or awireless interface supporting for example Bluetooth®. The keypad 708 canrepresent a numeric keypad commonly used by phones, and/or a QWERTYkeypad with alphanumeric keys. The UI 704 can further include a display710 such as monochrome or color LCD (Liquid Crystal Display), OLED(Organic Light Emitting Diode) or other suitable display technology forconveying images to an end user of the communication device 700. In anembodiment where the display 710 is touch-sensitive, a portion or all ofthe keypad 708 can be presented by way of the display 710 withnavigation features.

The display 710 can use touch screen technology to also serve as a userinterface for detecting user input. As a touch screen display, thecommunication device 700 can be adapted to present a user interface withgraphical user interface (GUI) elements that can be selected by a userwith a touch of a finger. The touch screen display 710 can be equippedwith capacitive, resistive or other forms of sensing technology todetect how much surface area of a user's finger has been placed on aportion of the touch screen display. This sensing information can beused to control the manipulation of the GUI elements or other functionsof the user interface. The display 710 can be an integral part of thehousing assembly of the communication device 700 or an independentdevice communicatively coupled thereto by a tethered wireline interface(such as a cable) or a wireless interface.

The UI 704 can also include an audio system 712 that utilizes audiotechnology for conveying low volume audio (such as audio heard inproximity of a human ear) and high volume audio (such as speakerphonefor hands free operation). The audio system 712 can further include amicrophone for receiving audible signals of an end user. The audiosystem 712 can also be used for voice recognition applications. The UI704 can further include an image sensor 713 such as a charged coupleddevice (CCD) camera for capturing still or moving images.

The power supply 714 can utilize common power management technologiessuch as replaceable and rechargeable batteries, supply regulationtechnologies, and/or charging system technologies for supplying energyto the components of the communication device 700 to facilitatelong-range or short-range portable applications. Alternatively, or incombination, the charging system can utilize external power sources suchas DC power supplied over a physical interface such as a USB port orother suitable tethering technologies.

The location receiver 716 can utilize location technology such as aglobal positioning system (GPS) receiver capable of assisted GPS foridentifying a location of the communication device 700 based on signalsgenerated by a constellation of GPS satellites, which can be used forfacilitating location services such as navigation. The motion sensor 718can utilize motion sensing technology such as an accelerometer, agyroscope, or other suitable motion sensing technology to detect motionof the communication device 700 in three-dimensional space. Theorientation sensor 720 can utilize orientation sensing technology suchas a magnetometer to detect the orientation of the communication device700 (north, south, west, and east, as well as combined orientations indegrees, minutes, or other suitable orientation metrics).

The communication device 700 can use the transceiver 702 to alsodetermine a proximity to a cellular, WiFi, Bluetooth®, or other wirelessaccess points by sensing techniques such as utilizing a received signalstrength indicator (RSSI) and/or signal time of arrival (TOA) or time offlight (TOF) measurements. The controller 706 can utilize computingtechnologies such as a microprocessor, a digital signal processor (DSP),programmable gate arrays, application specific integrated circuits,and/or a video processor with associated storage memory such as Flash,ROM, RAM, SRAM, DRAM or other storage technologies for executingcomputer instructions, controlling, and processing data supplied by theaforementioned components of the communication device 700.

Other components not shown in FIG. 7 can be used in one or moreembodiments of the subject disclosure. For instance, the communicationdevice 700 can include a reset button (not shown). The reset button canbe used to reset the controller 706 of the communication device 700. Inyet another embodiment, the communication device 700 can also include afactory default setting button positioned, for example, below a smallhole in a housing assembly of the communication device 700 to force thecommunication device 700 to re-establish factory settings. In thisembodiment, a user can use a protruding object such as a pen or paperclip tip to reach into the hole and depress the default setting button.The communication device 700 can also include a slot for adding orremoving an identity module such as a Subscriber Identity Module (SIM)card. SIM cards can be used for identifying subscriber services,executing programs, storing subscriber data, and so forth.

The communication device 700 as described herein can operate with moreor less of the circuit components shown in FIG. 7. These variantembodiments can be used in one or more embodiments of the subjectdisclosure.

The communication device 700 can be adapted to perform the functions ofthe UE 108 of FIG. 1, the media processor 506, the media devices 508, orthe portable communication devices 516 of FIG. 5, as well as the IMS CDs501-502 and PSTN CDs 503-505 of FIG. 5. It will be appreciated that thecommunication device 700 can also represent other devices that canoperate in systems 100, 200, 300 of FIGS. 1, 2 and/or 3, communicationsystems 500 of FIG. 5 such as a gaming console and a media player. Inaddition, the controller 706 can be adapted in various embodiments toperform one or more of the functions 562-568.

Upon reviewing the aforementioned embodiments, it would be evident to anartisan with ordinary skill in the art that said embodiments can bemodified, reduced, or enhanced without departing from the scope of theclaims described below. For example, the intelligence in selecting anetwork node to support GCS services can be provided by an entity otherthan the network service provider or the content service provider.Consider an entity providing a service to network and/or content serviceproviders to facilitate a coordination of GCS services according to oneor more service criteria. The network and/or content providers cansubscribe to the service, e.g., obtaining guidance in configuringnetwork elements to deliver GCS services consistent with the particularcriteria. In such instances, the intelligence can be included on one ofthe network nodes, or on another server, e.g., a server resident at adata center and/or otherwise accessible by a PDN 106, such as theInternet or World-Wide-Web. Other embodiments can be used in the subjectdisclosure.

It should be understood that devices described in the exemplaryembodiments can be in communication with each other via various wirelessand/or wired methodologies. The methodologies can be links that aredescribed as coupled, connected and so forth, which can includeunidirectional and/or bidirectional communication over wireless pathsand/or wired paths that utilize one or more of various protocols ormethodologies, where the coupling and/or connection can be direct (e.g.,no intervening processing device) and/or indirect (e.g., an intermediaryprocessing device such as a router).

FIG. 8 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 800 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as the GCS management engine 224, 530, the OSS220, the media processor 506, the BMSC 296, the MBMS-GW 126, the GCS-AS202 and other devices of FIGS. 1-3 and 5. In some embodiments, themachine may be connected (e.g., using a network 826) to other machines.In a networked deployment, the machine may operate in the capacity of aserver or a client user machine in a server-client user networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

The computer system 800 may include a processor (or controller) 802(e.g., a central processing unit (CPU)), a graphics processing unit(GPU, or both), a main memory 804 and a static memory 806, whichcommunicate with each other via a bus 808. The computer system 800 mayfurther include a display unit 810 (e.g., a liquid crystal display(LCD), a flat panel, or a solid state display). The computer system 800may include an input device 812 (e.g., a keyboard), a cursor controldevice 814 (e.g., a mouse), a disk drive unit 816, a signal generationdevice 818 (e.g., a speaker or remote control) and a network interfacedevice 820. In distributed environments, the embodiments described inthe subject disclosure can be adapted to utilize multiple display units810 controlled by two or more computer systems 800. In thisconfiguration, presentations described by the subject disclosure may inpart be shown in a first of the display units 810, while the remainingportion is presented in a second of the display units 810.

The disk drive unit 816 may include a tangible computer-readable storagemedium 822 on which is stored one or more sets of instructions (e.g.,software 824) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above. Theinstructions 824 may also reside, completely or at least partially,within the main memory 804, the static memory 806, and/or within theprocessor 802 during execution thereof by the computer system 800. Themain memory 804 and the processor 802 also may constitute tangiblecomputer-readable storage media.

Dedicated hardware implementations including, but not limited to,application specific integrated circuits, programmable logic arrays andother hardware devices can likewise be constructed to implement themethods described herein. Application specific integrated circuits andprogrammable logic array can use downloadable instructions for executingstate machines and/or circuit configurations to implement embodiments ofthe subject disclosure. Applications that may include the apparatus andsystems of various embodiments broadly include a variety of electronicand computer systems. Some embodiments implement functions in two ormore specific interconnected hardware modules or devices with relatedcontrol and data signals communicated between and through the modules,or as portions of an application-specific integrated circuit. Thus, theexample system is applicable to software, firmware, and hardwareimplementations.

In accordance with various embodiments of the subject disclosure, theoperations or methods described herein are intended for operation assoftware programs or instructions running on or executed by a computerprocessor or other computing device, and which may include other formsof instructions manifested as a state machine implemented with logiccomponents in an application specific integrated circuit or fieldprogrammable gate array. Furthermore, software implementations (e.g.,software programs, instructions, etc.) including, but not limited to,distributed processing or component/object distributed processing,parallel processing, or virtual machine processing can also beconstructed to implement the methods described herein. It is furthernoted that a computing device such as a processor, a controller, a statemachine or other suitable device for executing instructions to performoperations or methods may perform such operations directly or indirectlyby way of one or more intermediate devices directed by the computingdevice.

While the tangible computer-readable storage medium 822 is shown in anexample embodiment to be a single medium, the term “tangiblecomputer-readable storage medium” should be taken to include a singlemedium or multiple media (e.g., a centralized or distributed database,and/or associated caches and servers) that store the one or more sets ofinstructions. The term “tangible computer-readable storage medium” shallalso be taken to include any non-transitory medium that is capable ofstoring or encoding a set of instructions for execution by the machineand that cause the machine to perform any one or more of the methods ofthe subject disclosure. The term “non-transitory” as in a non-transitorycomputer-readable storage includes without limitation memories, drives,devices and anything tangible but not a signal per se.

The term “tangible computer-readable storage medium” shall accordinglybe taken to include, but not be limited to: solid-state memories such asa memory card or other package that houses one or more read-only(non-volatile) memories, random access memories, or other re-writable(volatile) memories, a magneto-optical or optical medium such as a diskor tape, or other tangible media which can be used to store information.Accordingly, the disclosure is considered to include any one or more ofa tangible computer-readable storage medium, as listed herein andincluding art-recognized equivalents and successor media, in which thesoftware implementations herein are stored.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the disclosure is not limited to such standards andprotocols. Each of the standards for Internet and other packet switchednetwork transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) representexamples of the state of the art. Such standards are from time-to-timesuperseded by faster or more efficient equivalents having essentiallythe same functions. Wireless standards for device detection (e.g.,RFID), short-range communications (e.g., Bluetooth®, WiFi, Zigbee®), andlong-range communications (e.g., WiMAX, GSM, CDMA, LTE, LTE-Advanced)can be used by computer system 800.

The illustrations of embodiments described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other embodiments will be apparentto those of skill in the art upon reviewing the above description. Theexemplary embodiments can include combinations of features and/or stepsfrom multiple embodiments. Other embodiments may be utilized and derivedtherefrom, such that structural and logical substitutions and changesmay be made without departing from the scope of this disclosure. Figuresare also merely representational and may not be drawn to scale. Certainproportions thereof may be exaggerated, while others may be minimized.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense.

Although specific embodiments have been illustrated and describedherein, it should be appreciated that any arrangement which achieves thesame or similar purpose may be substituted for the embodiments describedor shown by the subject disclosure. The subject disclosure is intendedto cover any and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, can be used in the subject disclosure.For instance, one or more features from one or more embodiments can becombined with one or more features of one or more other embodiments. Inone or more embodiments, features that are positively recited can alsobe negatively recited and excluded from the embodiment with or withoutreplacement by another structural and/or functional feature. The stepsor functions described with respect to the embodiments of the subjectdisclosure can be performed in any order. The steps or functionsdescribed with respect to the embodiments of the subject disclosure canbe performed alone or in combination with other steps or functions ofthe subject disclosure, as well as from other embodiments or from othersteps that have not been described in the subject disclosure. Further,more than or less than all of the features described with respect to anembodiment can also be utilized.

Less than all of the steps or functions described with respect to theexemplary processes or methods can also be performed in one or more ofthe exemplary embodiments. Further, the use of numerical terms todescribe a device, component, step or function, such as first, second,third, and so forth, is not intended to describe an order or functionunless expressly stated so. The use of the terms first, second, thirdand so forth, is generally to distinguish between devices, components,steps or functions unless expressly stated otherwise. Additionally, oneor more devices or components described with respect to the exemplaryembodiments can facilitate one or more functions, where the facilitating(e.g., facilitating access or facilitating establishing a connection)can include less than every step needed to perform the function or caninclude all of the steps needed to perform the function.

In one or more embodiments, a processor (which can include a controlleror circuit) has been described that performs various functions. Itshould be understood that the processor can be multiple processors,which can include distributed processors or parallel processors in asingle machine or multiple machines. The processor can be used insupporting a virtual processing environment. The virtual processingenvironment may support one or more virtual machines representingcomputers, servers, or other computing devices. In such virtualmachines, components such as microprocessors and storage devices may bevirtualized or logically represented. The processor can include a statemachine, application specific integrated circuit, and/or programmablegate array including a Field PGA. In one or more embodiments, when aprocessor executes instructions to perform “operations”, this caninclude the processor performing the operations directly and/orfacilitating, directing, or cooperating with another device or componentto perform the operations.

The Abstract of the Disclosure is provided with the understanding thatit will not be used to interpret or limit the scope or meaning of theclaims. In addition, in the foregoing Detailed Description, it can beseen that various features are grouped together in a single embodimentfor the purpose of streamlining the disclosure. This method ofdisclosure is not to be interpreted as reflecting an intention that theclaimed embodiments require more features than are expressly recited ineach claim. Rather, as the following claims reflect, inventive subjectmatter lies in less than all features of a single disclosed embodiment.Thus the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separately claimedsubject matter.

What is claimed is:
 1. A system, comprising: a processing systemincluding a processor; and a memory that stores executable instructionsthat, when executed by the processor, facilitate performance ofoperations, comprising: determining an efficiency metric for each of aplurality of broadcast multicast service centers (BMSCs); selecting aBMSC of the plurality of BMSCs to obtain a selected BMSC based on thedetermining of the efficiency metric; and initiating a multimediabroadcast multicast (MBMS) service using the selected BMSC, whereincontent is distributed to mobile user equipment by way of the MBMSservice.
 2. The system of claim 1, wherein the content is disseminatedover a network, and wherein the operations further comprise: receiving arequest to initiate the MBMS service; and identifying criteria, based onthe request, for selecting candidate group communication service (GCS)nodes on the network, wherein the selecting the BMSC comprises selectinga GCS node from the candidate GCS nodes.
 3. The system of claim 1,wherein the content is distributed within a target geographical regionusing a common radio channel.
 4. The system of claim 1, wherein theselecting the BMSC comprises determining whether the efficiency metricsatisfies an efficiency criterion.
 5. The system of claim 1, wherein theoperations further comprise evaluating the efficiency metric for each ofthe plurality of BMSCs to obtain an evaluation result, wherein theefficiency metric is based on measured parameters related to the BMSCs.6. The system of claim 5, wherein the plurality of BMSCs are accessibleby way of a network, and wherein the operations further comprise:detecting a failure of the network, the selected BMSC, or both; andresponsive to the detecting the failure: selecting an alternative BMSCof the plurality of BMSCs to obtain a selected alternative BMSC based onthe evaluation result; and initiating an alternative MBMS service usingthe selected alternative BMSC.
 7. The system of claim 5, wherein theselecting the BMSC comprises selecting a subset of the plurality ofBMSCs to obtain a selected subset of BMSCs based on the evaluationresult, wherein the initiating the MBMS service comprises facilitating aplurality of MBMS services using the selected subset of BMSCs.
 8. Thesystem of claim 1, wherein the efficiency metric comprises one ofresource utilization metrics, associated wireless serving areas,proximity to a group communication service processor providing a contentitem, loading metrics, latency factors, round trip time latencymeasurements, or any combination thereof.
 9. The system of claim 8,wherein the efficiency metric further comprises characteristics ofnetwork connections to the plurality of BMSCs.
 10. The system of claim1, wherein the plurality of BMSCs are connected to a group communicationservice application server (GCS-AS) through a signaling controller. 11.The system of claim 10, wherein the operations further comprisereceiving a request from the GCS-AS to initiate the MBMS service.
 12. Amethod comprising: determining, by a processing system including aprocessor, an efficiency metric for each of a plurality of broadcastmulticast service centers (BMSCs); selecting, by the processing system,a BMSC of the plurality of BMSCs to obtain a selected BMSC based on thedetermining of the efficiency metric, wherein the selecting comprisesdetermining whether the efficiency metric satisfies an efficiencycriterion; and initiating, by the processing system, a multimediabroadcast multicast (MBMS) service using the selected BMSC, whereincontent is distributed to mobile user equipment within a targetgeographical region using a common radio channel by way of the MBMSservice.
 13. The method of claim 12, further comprising evaluating, bythe processing system, the efficiency metric for each of the pluralityof BMSCs to obtain an evaluation result, wherein the efficiency metricis based on measured parameters related to the BMSCs.
 14. The method ofclaim 13, wherein the plurality of BMSCs are accessible by way of anetwork, and further comprising: detecting, by the processing system, afailure of the network, the selected BMSC, or both; and responsive tothe detecting the failure: selecting, by the processing system, analternative BMSC of the plurality of BMSCs to obtain a selectedalternative BMSC based on the evaluation result; and initiating, by theprocessing system, an alternative MBMS service using the selectedalternative BMSC.
 15. The method of claim 12, wherein the efficiencymetric comprises one of resource utilization metrics, associatedwireless serving areas, proximity to a group communication serviceprocessor providing a content item, loading metrics, latency factors,round trip time latency measurements, or any combination thereof. 16.The method of claim 15, wherein the efficiency metric further comprisescharacteristics of network connections to the plurality of BMSCs.
 17. Amachine-readable storage medium, comprising executable instructionsthat, when executed by a processor, facilitate performance ofoperations, comprising: determining an efficiency metric for each of aplurality of broadcast multicast service centers (BMSCs); selecting aBMSC of the plurality of BMSCs to obtain a selected BMSC based on thedetermining of the efficiency metric; and initiating a multimediabroadcast multicast (MBMS) service using the selected BMSC, whereincontent is distributed to mobile user equipment within a targetgeographical region using a common radio channel by way of the MBMSservice.
 18. The machine-readable storage medium of claim 17, whereinthe selecting the BMSC comprises determining whether the efficiencymetric satisfies an efficiency criterion.
 19. The machine-readablestorage medium of claim 17, wherein the operations further compriseevaluating the efficiency metric for each of the plurality of BMSCs toobtain an evaluation result, wherein the efficiency metric is based onmeasured parameters related to the BMSCs.
 20. The machine-readablestorage medium of claim 17, wherein the efficiency metric comprises oneof resource utilization metrics, associated wireless serving areas,proximity to a group communication service processor providing a contentitem, loading metrics, latency factors, round trip time latencymeasurements, or any combination thereof.